Obtaining virtual machine images from virtualization environments

ABSTRACT

Techniques are described for facilitating sharing and reuse of executable software images between multiple execution environments. In at least some situations, the executable software images are virtual machine images (e.g., images that are bootable or otherwise loadable by a virtual machine in a particular virtualization environment, and that each include operating system software and/or software for one or more application programs, optionally along with one or more hard disks or other representations of stored data). The described techniques may include use of an image conversion tool that is configured to support interactions with multiple distinct types of source execution environments to extract executable software images from those environments, and to modify extracted software images for execution in one or more distinct types of destination execution environments, optionally as directed by one or more users via a GUI provided by the image conversion tool.

BACKGROUND

The advent of virtualization technologies for commodity hardware hasprovided benefits for many customers with diverse needs, allowingvarious computing resources to be efficiently and securely sharedbetween multiple customers. For example, virtualization environmentssuch as those provided by VMWare, XEN, Hyper-V and User-Mode Linux mayallow a single physical computing machine to be shared among multipleusers by providing each user with one or more virtual machines hosted bythe single physical computing machine. Each such virtual machine may bea software simulation acting as a distinct logical computing system thatprovides users with the illusion that they are the sole operators andadministrators of a given hardware computing resource, while alsoproviding application isolation and security among the various virtualmachines. Furthermore, some virtualization technologies are capable ofproviding virtual resources that span one or more physical resources,such as a single virtual machine with multiple virtual processors thatactually spans multiple distinct physical computing systems. However,each virtualization environment typically operates using data formatsand interfaces specific to that virtualization environment, inhibitinginteroperability between virtualization environments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a network diagram illustrating an example environment in whichan image conversion tool may be used.

FIG. 2 illustrates an example of use of an image conversion tool.

FIG. 3 is a block diagram illustrating an example computing systemsuitable for executing an embodiment of an image conversion tool.

FIGS. 4A and 4B are a flow diagram of an example embodiment of an ImageConversion Tool routine.

FIG. 5 is a flow diagram of an example embodiment of a routine thatprovides functionality of a source virtualization environment.

FIG. 6 is a flow diagram of an example embodiment of a routine thatprovides functionality of a destination virtualization environment.

DETAILED DESCRIPTION

Techniques are described for facilitating sharing and reuse ofexecutable software images between multiple execution environments. Thedescribed techniques include use of an image conversion tool in at leastsome embodiments, such as an image conversion tool that is configured tosupport interactions with multiple distinct types of source executionenvironments to extract executable software images from those sourceexecution environments, and to modify extracted software images forexecution in one or more distinct types of destination executionenvironments. In at least some such embodiments, the image conversiontool may provide a GUI (“graphical user interface”) via which one ormore users of the image conversion tool specify and configure particulartypes of operations to be performed. In at least some embodiments, theexecutable software images are virtual machine images (e.g., images thatare bootable or otherwise loadable by a virtual machine in a particularsource virtualization environment, and that each include operatingsystem software and/or software for one or more application programs,optionally along with one or more hard disks or other representations ofstored data). Additional details related to sharing and reuse ofexecutable software images are included below, and the describedtechniques are automatically performed in at least some embodiments byone or more image conversion tools.

The described techniques may be provided in a variety of manners invarious environments and situations. For example, some softwareexecution environments may provide one or more executing pieces ofsoftware that provide defined APIs (“application programminginterfaces”) or other defined interfaces, and the image conversion toolmay programmatically invoke or otherwise access such provided interfaces(e.g., over one or more intervening connections or networks), includingto initiate the providing by the software execution environment of datacorresponding to a particular software image of interest. In addition,some software execution environments may store data corresponding tosome or all software images in a manner that is remotely accessible, andwith the data in a format that may be manipulated by the imageconversion tool, and if so the image conversion tool mayprogrammatically access and retrieve such data for a software image ofinterest. Other types of interactions may be performed between the imageconversion tool and a software execution environment in otherembodiments in order to extract data corresponding to a software imageof interest (e.g., by executing software of the image conversion toolwithin a virtual machine or other execution environment of the softwareexecution environment). In addition, in some embodiments and situations,the image conversion tool may receive data corresponding to a softwareimage of interest in other manners, such as if a user uploads that datadirectly to the image conversion tool (e.g., after the user obtains thedata from a particular execution environment).

In addition, a particular image conversion tool may be designed and/orconfigured to support particular source execution environments invarious manners, such as by storing configuration information that isspecific to each source execution environment. In at least someembodiments, the image conversion tool may further be designed with anarchitecture that enables support for additional execution environmentsto be later added to the image conversion tool, such as by providing astandardized group of types of interactions that may be performed withexecution environments, and then storing information specific to eachexecution environment to indicate which types of interactions areavailable and the details of how they are performed in a manner specificto that execution environment. In some such embodiments, theconfiguration information specific to a particular software executionenvironment may be provided in whole or in part in a module specific tothat software execution environment, such as in a plug-in module that isadded to the image conversion tool (or accessed by the image conversiontool) after the image conversion tool creation is completed.

After the data corresponding to a software image is obtained by theimage conversion tool, the image conversion tool may modify or otherwisemanipulate the data in various manners in order to prepare it to beexecuted in one or more distinct destination execution environments. Theimage conversion tool may further provide the data for the softwareimage for use in a destination execution environment in various manners,including by transmitting the data over one or more connections ornetworks to the destination execution environment. Non-exclusiveexamples of types of data manipulations of a software image may includechanging a data format in which the data is stored, adding additionaldata (e.g., to correspond to one or more software libraries or driversor other programs that are available for execution or other use whilethe software image is executing), changing references within thesoftware image to how and where data for use by the software image isstored, combining or separating the data into different sizes orconfigurations supported by the destination execution environment,compressing the data, encrypting the data, etc.

The use of the described techniques provides a variety of benefits invarious embodiments. For example, by enabling a user to direct an imageconversion tool to interact with and extract executable virtual machineimages from any of multiple distinct types of source virtualizationenvironments, the user may consolidate use of multiple distinct types ofvirtual machine images in a single destination virtualizationenvironment, without losing time and effort involved in creating thevarious virtual machine images. Furthermore, in at least some suchembodiments and situations, some or all of the various source virtualmachine images may be modified in various manners that are supported bythe destination virtualization environment, including to optionallystandardize aspects of the various source virtual machine images and/orto add new capabilities available in the destination virtualizationenvironment that were not previously available or used in sourcevirtualization environments from which the source virtual machine imagesare extracted.

Various types of virtualization environments and other software imageexecution environments may be supported in various embodiments. Anon-exclusive list of examples of such software image executionenvironments include those provided by or with VMWare Server, VMWareWorkstation, XenServer, Hyper-V Server, VirtualBox, KVM (“Kernel-basedVirtual Machine”), User-Mode Linux, OpenVZ (“Open Virtualization”), etc.In addition, virtual machine images and other software images executableby or otherwise supported by such software image execution environmentsmay store different types of programs and/or non-executable data invarious manners.

For illustrative purposes, some embodiments are described below in whichspecific types of operations are performed and specific types of dataused, including to interact with virtualization environments to extract,modify and execute virtual machine images. These examples are providedfor illustrative purposes and are simplified for the sake of brevity,and the inventive techniques may be used in a wide variety of othersituations, some of which are discussed below.

FIG. 1 is a network diagram illustrating an example of various systemsthat may interact in order to enable an image conversion tool 150 toperform various of the described techniques. In particular, the imageconversion tool may interact with various source virtualizationenvironments in order to obtain data corresponding to source virtualmachine images that execute in those source virtualization environments,and may modify the obtained data for a source virtual machine image toenable the virtual machine image to execute in a distinct type ofdestination virtualization environment. In the illustrated example, atleast some of the operations of the image conversion tool 150 aredirected by an associated user 175 of the image conversion tool,although in other embodiments at least some of the operations of theimage conversion tool may instead be performed in an automated manner.

In particular, in the illustrated embodiment, the user 175 has access toone or more virtual machine images 125 that execute as part of a sourcevirtualization environment A 120 a. For example, in some suchsituations, the user 175 may execute the virtualization environment A120 a on one or more computing systems (not shown) that are undercontrol of the user, such as may be executing at a facility or locationof the user, or the user 175 may instead interact with thevirtualization environment A over one or more intervening networks (notshown).

In the illustrated example, the user 175 desires to convert at least oneof the virtual machine images 125 from source virtualization environmentA to enable the converted virtual machine image to be executed in adistinct destination execution environment 180, with the destinationexecution environment 180 being of a different type of virtualizationenvironment than that of source virtualization environment A 120 a inthis example. Accordingly, in this example, the user obtains access to(e.g., downloads) a copy of the virtual machine image conversion tool150 for use in the virtual machine image conversion process. The user175 may, for example, execute the image conversion tool 150 on one ormore computing systems (not shown) that are local to the virtualizationenvironment A 120 a, such as at the same facility or other location(e.g., on a common local area network), including in some embodimentsand situations to optionally execute the conversion tool 150 on one ormore computing systems that are part of the virtualization environment A120 a. In other embodiments, the conversion tool 150 may executeremotely from the virtualization environment A 120 a, such as over oneor more public networks.

In the illustrated embodiment, the image conversion tool 150 supportsinteractions with multiple distinct types of source virtualizationenvironments from which virtual machine images or other software imagesmay be extracted, so that the extracted software images may bemanipulated to enable their execution in a distinct destinationexecution environment. For example, the image conversion tool 150 may bedesigned and/or configured to support a fixed number and type of sourcevirtualization environments, or may instead have an architecture thatenables configuration information specific to a particular sourcevirtualization environment to be provided to the image conversion toolafter its initial creation. In the illustrated embodiment, the imageconversion tool 150 may support multiple plug-in modules 170 that eachprovides an interface to one of multiple distinct types of sourcevirtualization environments.

Accordingly, in the illustrated example, the user 175 performs one ormore interactions 110 with GUI 155 of the image conversion tool 150.Such interactions may include, for example, identifying a specificsource virtualization environment with which the image conversion tool150 will interact, specifying a particular source image to be extractedfrom a source virtualization environment, and providing configurationinformation to control the manipulation and provision of the extractedimage for a particular destination execution environment.

In this example, the interactions 110 of the user 175 with the GUI 155include the user identifying source virtualization environment A 120 a,and accordingly the image conversion tool 150 selects a module 170 aspecific to that source virtualization environment. The image conversiontool 150 then uses the selected module 170 a to perform one or moreinteractions 112 with the virtualization environment A 120 a, such as insome embodiments to interact with a manager module 135 of the sourcevirtualization environment to obtain data for at least one virtualmachine image 125 that is executing in the source virtualizationenvironment or stored in or accessible to the source virtualizationenvironment. For example, the manager module 135 may provide one or moreAPIs (not shown) that enable programmatic interactions between themodule 170 a and the manager module 135, while in other embodiments theinteractions 112 may include the image conversion tool 150 interactingdirectly with stored data corresponding to a particular virtual machineimage 125 of interest. For example, each virtual machine image 125 mayinclude one or more hard disks 130 that store data representing thevirtual machine image, and such hard disk data may be persistentlystored on non-volatile storage accessible to the virtualizationenvironment A (e.g., on one or more local physical hard disks of one ormore computing systems executing the virtualization environment A) whilethe virtual machine image is not executing. Thus, the interactions 112may instead in some embodiments and situations interact directly withone or more non-volatile storage devices (or a storage manager interfaceto such devices) in order to obtain access to stored data for such harddisks.

The data corresponding to a particular virtual machine image 125 that isextracted from the source virtualization environment A 120 a may havevarious forms in various embodiments, such as one or more streams of rawdata, one or more streams of compressed data, one or more downloadablepieces of data (e.g., files), etc. In some source virtualizationenvironments, the hard disk data may be stored in a standardized formatfor that source virtualization environment, which the correspondinginterface module 170 may access and download. Such data formats mayinclude, for example, VHD (“Virtual Hard Disk”), VMDK (“Virtual MachineDisk”), VDI (“Virtual Disk Image”), OVF (“Open Virtualization Format”),etc.

After the data corresponding to a particular virtual machine image isextracted via the interactions 112, the image conversion tool 150performs one or more modifications or other manipulations of theextracted data in order to prepare it for a distinct virtualizationenvironment available in the destination execution environment 180. Forexample, the data manipulations of the data for the virtual machineimage may include changing a data format in which the data is stored,adding additional data (e.g., to correspond to one or more softwarelibraries or drivers or other programs that are available for executionor other use while the virtual machine image is executing), changingreferences within the virtual machine image to how and where data foruse by the virtual machine image is stored, etc. While not illustratedin FIG. 1, the image conversion tool 150 may store copies of some or allvirtual machine images that it handles, whether temporarily while theprocessing is performed or more permanently (e.g., until the userindicates that processing of the virtual machine image is done). Suchstored copies may correspond to the virtual machine image data before,during and/or after its manipulation, and may be stored local to theimage conversion tool or on one or more remote storage devices.

After the extracted data for a particular virtual machine image isprepared for the destination execution environment, an interface 160specific to the destination environment is used to perform one or moreinteractions 114 with the destination execution environment to providethe modified data of the virtual machine image to the destinationexecution environment, to enable the virtual machine image to beexecuted by the destination execution environment based on the modifieddata. In the illustrated embodiment, the interactions 114 occur over oneor more networks 100, although in other embodiments, the imageconversion tool 150 may execute locally to a particular destinationexecution environment (e.g., within that destination executionenvironment, or otherwise as part of the capabilities provided by thatdestination execution environment). The interactions 114 may in thisexample involve interacting with a manager module 195 at the destinationexecution environment, such as to interact with one or more APIsprovided by the manager module.

After the modified data for the virtual machine image is provided to thedestination execution environment, the data may be stored as part of avirtual machine image 185 in the destination execution environment, suchas to correspond to one or more hard disks 190 that represent thevirtual machine image. While not illustrated in this example, in otherembodiments the interactions 114 may include providing the modified datafor the virtual machine image in other manners, such as to instead storethe modified data in a separate storage service that is distinct frombut accessible to the destination execution environment, to provide acopy of the modified data to the user 175 (e.g., on a transportablecomputer-readable storage medium), etc. In addition, in this example,the image conversion tool 150 interacts 114 directly with thedestination execution environment 180, although in other embodiments theimage conversion tool may instead first interact with one or moreoptional modules 140, such as if functionality of the image conversiontool is in some embodiments separated into multiple modules, such as onemodule local to the source virtualization environment and another modulelocal to the destination execution environment. If so, the module 140may perform some or all of the interactions with the destinationexecution environment 180 that occur in a manner specific to thatdestination execution environment.

As previously noted, the image conversion tool 150 may, in at least someembodiments and situations, be configured to support interactions withmultiple different types of source virtualization environments. Thus, inthe illustrated example, the user 175 (or a different user, not shown)may perform additional interactions with the image conversion tool inorder to similarly access and extract data for one or more virtualmachine images or other software images from a distinct virtualizationenvironment of a distinct type from that of the source virtualizationenvironment A 120 a, such as to interact with a distinct virtualizationenvironment N 120 n. To do so, the image conversion tool 150 in theillustrated embodiment uses a distinct interface module 170 n that isconfigured to perform interactions in a manner specific to the sourcevirtualization environment N 120 n, by performing one or moreinteractions 118. In addition, in this example the source virtualizationenvironment N 120 n is remote from the image conversion tool 150, andthus the interactions 118 occur over one or more networks 100. It willbe appreciated that other configurations of systems and correspondinginteractions may be provided in other embodiments.

FIG. 2 illustrates additional details regarding examples of interactionsthat may be performed between an image conversion tool and a sourcevirtualization environment. In the example of FIG. 2, the imageconversion tool 150 of FIG. 1 is illustrated with additional detailscorresponding to internal modules of the tool and related datainteractions that may occur.

In particular, in the example of FIG. 2, after a user (not shown)interacts with a GUI provided by a module 155, the GUI module performone or more interactions 252 with an image extractor module 242 of theimage conversion tool 150. In this example, the image extractor module242 may, for example, control interactions with various sourcevirtualization environments in a manner that is partially or whollyindependent of the particular interaction techniques used by particularsource virtualization environments. The image extractor module 242 mayfurther perform additional operations, such as to provide informationreceived from a source virtualization environment to the GUI to enablefurther user interactions, and to initiate additional actions involvingextracted data that is received from a source virtualizationenvironment, as discussed further below. In other embodiments,directions may be provided to the image extractor module 242 in othermanners, such as may be initiated by a user via programmaticinteractions with the tool 150 that do not use the GUI, or via anautomated determination by the tool 150 that is not initiated by a user.

In this example, the user has indicated to interact with the sourcevirtualization environment A 120 a of FIG. 1, and accordingly theinterface plug-in module 170 a of the image conversion tool is used bythe image extractor module 242. Thus, the image extractor moduleperforms one or more interactions 254 with the interface plug-in module170 a to initiate interactions with the source virtualizationenvironment A, in order to obtain corresponding information and toextract one or more virtual machine images as designated. For example,the image extractor module 242 may specify types of interactions toperform with the source virtualization environment A (e.g., to obtaindata about available virtual machine images or other software images, toextract data for an indicated virtual machine image or other softwareimage, etc.), and the module 170 a may implement those interaction typesin a manner specific to the source virtualization environment A.

In the illustrated embodiment, the source virtualization environment A120 a of FIG. 1 includes or is supported by one or more computingsystems 220, with an illustrated example computing system 220 aillustrated in FIG. 2. In this example, the computing system 220 a mayinclude one or more CPU processors 205, various types of I/O components225, memory 230, and storage 210, with additional details related tosuch hardware components discussed with respect to FIG. 3. In thisexample, the computing system 220 a provides multiple virtual machines234 that are part of the memory 230, such as with each virtual machinehaving a dedicated portion of memory for use in executing a virtualmachine image. In addition, the memory 230 in this example executes ahypervisor monitor manager module 232 that controls operations of thevirtual machines 234.

In this example, the manager module 232 provides an API 235 specific tothe source virtualization environment A that enables programmaticinteractions with the manager module 232 by other executing programs,although in other embodiments such an API may be provided for a sourcevirtualization environment in other manners. Accordingly, the interfaceplug-in module 170 a of the image conversion tool may perform one ormore interactions 112 a with the API 235 of the manager module 232 inorder to obtain information about one or more of the virtual machineimages being executed in one or more of the virtual machines 234, orotherwise to obtain information about virtual machine images of thesource virtualization environment (e.g., that are registered or storedbut not currently executing). In addition, the interactions 112 a mayinclude supplying user-specific information to the source virtualizationenvironment A, such as after that information is received from the userof the image conversion tool, to enable the source virtualizationenvironment A to authenticate the user and/or access informationspecific to the user. In some embodiments, the manager module 232 mayobtain and provide data corresponding to one or more such virtualmachine images, such as data corresponding to a current state in memoryof an executing virtual machine image.

In addition, as previously noted, at least some such virtual machineimages that are executable by the source virtualization environment Amay each include one or more hard disks that store data corresponding tothe virtual machine image, including to store such hard disk data onnonvolatile storage while the virtual machine image is not executing. Inthis example, the storage 210 of the computing system 220 a may includeone or more such virtual machine hard disks 215, although in otherembodiments the hard disks may be stored remotely from the computingsystem 220 a on which the virtual machines execute. Accordingly, in atleast some embodiments and situations, the interface plug-in module 170a may be able to perform interactions 112 b directly with the computingsystem 220 a to obtain access to one or much such hard disks 215 fromstorage 210, such as to download or otherwise obtain copies of one ormore such hard disks 215. Such interactions 112 b may be performedinstead of or in addition to interactions 112 a, such as based on thetypes of interfaces available from a particular source virtualizationenvironment and the types of interactions to be performed.

After the data corresponding to a particular source virtual machineimage is obtained in this example by the interface plug-in module 170 afrom the computing system 220 a, the data is received by the imageextractor module 242 from the interface plug-in module. The imageextractor module then provides the data via one or more interactions 256to an internal image data manipulator module 246 of the image conversiontool 150. The image data manipulator module performs one or moremodifications to the obtained data in order to prepare the data forexecution in the destination execution environment, as described ingreater detail elsewhere, including to use data (not shown) specific tothe destination execution environment that is stored by or accessible tothe image conversion tool, such as to optionally add such data to themodified obtained data. The operations of the image data manipulatormodule may in some embodiments be directed at least in part based onconfiguration information specific to the destination executionenvironment, such as to support an ability of the image conversion toolto modify data for multiple distinct destination execution environmentsin some such embodiments, optionally by having distinct output interfacemodules specific to each such destination execution environment. Inaddition, the operations of the image data manipulator module 246 may bedirected at least in part by the user in some embodiments andsituations, such as to control particular manipulations that areperformed, based on interactions of the user with the GUI and asprovided to the image data manipulator module 246, whether directly (notshown) or via the image extractor module 242.

In the illustrated embodiment, after the image data manipulator modulemodifies the obtained data for the virtual machine image to correspondto the destination execution environment 180, the module 246 performsone or more interactions 258 with the destination environment interfacemodule 160 of the image conversion tool 150, which in this exampleinitiates one or more interactions 114 with the destination executionenvironment 180 to provide the modified data to the destinationexecution environment for execution as part of the virtual machine imagein the destination environment, as described with respect to FIG. 1. Theoperations of the modules 246 and/or 160 may further, in someembodiments, be directed based at least in part on other interactions bythe user with the GUI 155, such as to enable the user to specifyconfiguration information for parameters related to execution of thevirtual machine image in the destination execution environment. Suchconfiguration information may include details related to how and whenthe destination execution environment will execute the virtual machineimage, including based on types of computing resources to be used toperform the execution, an account of the user with the destinationexecution environment, etc.

In at least some embodiments, the image conversion tool 150 may furtherperform activities to assist the user in identifying virtual machineimages or other software images of source virtualization environmentsthat are not eligible or available to be modified and executed in aparticular destination execution environment. For example, the imageconversion tool 150 may identify information within a particularsoftware image that is not compatible with a particular destinationexecution environment, such as by inspecting portions of the softwareimage or its metadata, and provide corresponding warnings orfunctionality to the user. Such information for a software image mayinclude, for example, a particular operating system or other particularsoftware program that is included or not included in the software image,particular types of data formats, particular software image sizes ordata configurations, etc.

FIG. 3 is a block diagram illustrating one or more computing systemssuitable for executing an embodiment of an image conversion tool systemthat facilitates sharing and reuse of executable software images betweenmultiple execution environments. In particular, FIG. 3 illustrates oneor more computing systems 300 suitable for executing an embodiment of aimage conversion tool system 340, as well as multiple computing systems350 that are part of multiple source execution environments, and one ormore computing systems 370 that are part of one or more destinationexecution environments. Some or all of the execution environments may,for example, be virtualization environments in which virtual machineimages execute.

In the illustrated embodiment, the computing system(s) 300 each includesone or more CPU processors 305, various I/O components 310, storage 320,and memory 330, with the I/O components including a display 311, anetwork connection 312, a computer-readable media drive 313, and otherI/O devices 315 (e.g., a keyboard, mouse, speakers, etc.)—in otherembodiments, each computing 300 may include additional hardwarecomponents and/or lack some of the illustrated hardware components. Thecomputing systems 350 are each similarly illustrated as including one ormore CPU processors 351, various I/O components 352, storage 354, andmemory 357, and the computing systems 370 are each similarly illustratedas including one or more CPU processors 371, various I/O components 372,storage 374, and memory 377, although particular I/O components are notillustrated in this example.

In the illustrated embodiment, the image conversion tool system 340executes in memory 330 of a computing system 300, such as to includesoftware instructions that, when executed by one or more CPU processors305, program or otherwise configure the computing system 300 to performautomated operations to provide some or all of the described techniques.In addition, in the illustrated embodiment, one or more optionalenvironment-specific interface modules 336 may also execute in memory330, such as to perform operations similar to those of interface modules170 of FIG. 1, but in the illustrated embodiment may execute separatelyfrom the image conversion tool rather than being loaded within the imageconversion tool. In other embodiments, such modules 336 may instead beimplemented as part of the system 340, or alternatively may execute onanother computing system (not shown) and interact with the imageconversion tool system 340 over one or more networks 390.

The image conversion tool system 340 interacts with one or more users(not shown) of the computing system 300 to provide information aboutsoftware image conversion activities and to receive correspondinginstructions. In particular, the system 340 may interact with one ormore multiple supported source execution environments that are providedby the computing systems 350 in order to obtain data corresponding toone or more source software images, such as by interacting with one ormore manager modules 358 executing in memory 357 of each sourceexecution environment to obtain data corresponding to software images355, and/or by directly interacting with software images 359. While thevarious source execution environments are illustrated in this example asbeing separated from the system 340 by one or more networks 390, inother embodiments the system 340 may execute locally to at least one ofthe source execution environments. After data is obtained for a sourceimage, the system 340 may further modify that data in a manner specificto a particular destination execution environment, and interact with oneor more computing systems 370 of that destination execution environment(e.g., with one or more manager modules 378 executing in memory 377) tocreate a new corresponding software image 375 that is executable withinthe destination execution environment. As part of the operation of thesystem 340, it may store and use various environment-specificconfiguration information 322 (e.g., as part of one or more plug-ininterface modules for the system 340) and user information 324, and mayalso optionally store copies 326 of modified data for software images.Additional details related to operation of embodiments of an imageconversion tool are described elsewhere herein.

It will be appreciated that computing systems 300, 350 and 370 aremerely illustrative and are not intended to limit the scope ofembodiments of the present disclosure. The image conversion tool system340 may instead be executed by multiple interacting computing systems ordevices, and computing system(s) 300 may be connected to other devicesthat are not illustrated, including through one or more networks such asthe Internet, via the World Wide Web (“Web”), or other electroniccommunications network (e.g., cellular based network, public switchedtelephone network). More generally, a “client” or “server” computingsystem may comprise any combination of hardware and/or firmware that mayinteract in the described manners, optionally when programmed orotherwise configured with particular software, including (withoutlimitation) desktop or other computers (e.g., laptops, tablets, smartphones, etc.), cell phones, network devices, PDAs, wireless phones,pagers, electronic organizers, Internet appliances, network-attachedstorage, devices in a storage area network, television-based systems(e.g., using set-top boxes and/or personal/digital video recorders),game consoles, media players and various other consumer products thatinclude appropriate inter-communication capabilities. In addition, thefunctionality provided by the image conversion tool system 340 may insome embodiments be integrated as part of one or more other programs andsystems, and/or may be separated into multiple modules, as described ingreater detail elsewhere.

It will also be appreciated that, while various items are discussed orillustrated as being stored in volatile memory or on non-volatilestorage while being used, these items or portions of them can betransferred between memory and other storage devices for purposes ofmemory management and data integrity. Alternatively, in otherembodiments some or all of the software systems and/or modules mayexecute in memory on another device and communicate with the illustratedcomputing systems via inter-computer communication. Thus, in someembodiments, some or all of the described techniques may be performed byhardware means that include one or more processors and/or memory and/orstorage when configured by one or more software programs (e.g., theimage conversion tool) and/or data structures, such as by execution ofsoftware instructions of the one or more software programs and/or bystorage of such software instructions and/or data structures.Furthermore, in some embodiments, some or all of the describedtechniques of the indicated systems and/or modules may be implemented orprovided in other manners, such as at least partially using firmwareand/or hardware means, including, but not limited to, one or moreapplication-specific integrated circuits (ASICs), standard integratedcircuits, controllers (e.g., by executing appropriate instructions, andincluding microcontrollers and/or embedded controllers),field-programmable gate arrays (FPGAs), complex programmable logicdevices (CPLDs), etc. Some or all of the systems, modules and/or datastructures may also be stored (e.g., as software instructions orstructured data) on one or more non-transitory computer-readable storagemediums, such as a hard disk or flash drive or other non-volatilestorage device, volatile or non-volatile memory (e.g., RAM or flashRAM), a network storage device, or a portable media article (e.g., a DVDdisk, a CD disk, an optical disk, a flash memory device, etc.) to beread by an appropriate drive or via an appropriate connection. Thesystems, modules and data structures may also in some embodiments betransmitted via generated data signals (e.g., as part of a carrier waveor other analog or digital propagated signal) on a variety ofcomputer-readable transmission mediums, including wireless-based andwired/cable-based mediums, and may take a variety of forms (e.g., aspart of a single or multiplexed analog signal, or as multiple discretedigital packets or frames). Such computer program products may also takeother forms in other embodiments. Accordingly, embodiments of thepresent disclosure may be practiced with other computer systemconfigurations.

FIGS. 4A and 4B are a flow diagram of an example embodiment of an ImageConversion Tool routine 400. The routine may be provided by, forexample, execution of the image conversion tool 150 of FIGS. 1 and 2and/or the image conversion tool system 340 of FIG. 3, such as to assistusers in converting software images from one of multiple source softwareexecution environments for execution in at least one distinctdestination execution environment. In the illustrated embodiment, theroutine 400 is performed with respect to virtual machine images andcorresponding virtualization execution environments, although in otherembodiments other types of software images and/or execution environmentsmay be handled. In addition, in the illustrated embodiment, the routine400 may execute on one or more computing systems that are not part ofany source execution environments or destination execution environments,although in other embodiments some or all of the functionality of theroutine 400 may instead be integrated with or otherwise affiliated withone or more such execution environments (e.g., with a particulardestination execution environment).

The routine 400 begins at block 405 of FIG. 4A, where information isretrieved about multiple supported virtualization environments. Forexample, upon initialization of the image conversion tool, the tool mayretrieve configuration information regarding multiple supported sourcevirtualization environments and optionally one or more supporteddestination virtualization environments. As discussed in greater detailelsewhere, in some embodiments some or all of the configurationinformation for a specific virtualization environment may be included aspart of a plug-in or other interface module that may be loaded by theimage conversion tool, although in other embodiments the configurationinformation for a specific virtualization environment may be obtained bythe image conversion tool in other manners. In the illustratedembodiment, after block 405, the routine continues to block 410 topresent a graphical user interface to one or more users of the imageconversion tool, such as to enable a user of the image conversion toolto specify image conversion activities to be performed. In blocks415-490, the routine then proceeds to perform particular conversionactivities for virtual machine images as directed by the user.

In particular, after block 410, the routine continues to block 415 andwaits until an indication of user input or other data is received. Theroutine then continues to block 417 to determine if the input receivedis information specific to a current user. If so, the routine continuesto block 419 to receive and store the user-specific information. Asdiscussed in greater detail elsewhere, the user-specific information maybe of various types, such as login or other access information for theuser with respect to a specific source virtualization environment and/ora specific destination virtualization environment, user preferences withrespect to configuration options, particular user selections or otherdesignations of configuration parameters or other data to use, etc.

After block 419, or if it is instead determined in block 417 that thereceived user input was not user-specific information, the routinecontinues to block 420 to determine if the received input is a selectionby the user of a particular source virtualization environment, such asfrom information presented to the user via the graphical user interfaceof one or more such available source virtualization environments, orinstead as otherwise specified (e.g., by the user manually typing in orotherwise designating a particular source virtualization environment).If so, the routine continues to block 425 to interact with one or moreAPIs of the selected source virtualization environment to obtaininformation about one or more virtual machine images that are availablein that source environment, and to update the GUI accordingly. Theinteractions with the source environment may, for example, be based inpart on a particular user, such as based on use of user-specificinformation supplied with respect to block 419. In addition, theinteractions with the source environment may be based in part or inwhole on use of an interface module specific to the sourcevirtualization environment (e.g., to use APIs of the source environmentthat are specific to that source environment), or to otherwise useconfiguration information specific to the source virtualizationenvironment. In other embodiments (e.g., embodiments in which the sourcevirtualization environment does not provide appropriate APIs), theroutine may instead access data corresponding to one or more virtualmachine images in other manners, such as to download hard disk filesfrom the source virtualization environment.

After block 425, or if it is instead determined in block 420 that aselection of a source virtualization environment is not made, theroutine continues instead to block 440 to determine if a user selectionis made of a particular source virtual machine image available in aparticular source virtualization environment, such as for a sourcevirtualization environment previously selected in block 425, or asotherwise indicated—if so, the routine continues to block 445. Theparticular source virtual machine image may be indicated by the user invarious manners, such as via a selection from information presented tothe user via the graphical user interface of one or more such availablevirtual machine images, or instead as otherwise specified (e.g., by theuser manually typing in or otherwise designating a particular virtualmachine image). In other embodiments and situations, a particular usermay supply a particular source virtual machine image to the routine 400,such as with information about a type of source virtualizationenvironment with which the source virtual machine image, and if so block425 may not be performed in such situations.

The routine in block 445 interacts with one or more APIs of the selectedor otherwise indicated source virtualization environment to extract andreceive data corresponding to the selected source virtual machine image,such as a copy of that virtual machine image or of one or more harddisks represented within that virtual machine image. In a manner similarto that previously indicated with respect to block 425, the interactionswith the source virtualization environment may be performed based inpart or in whole via use of a module specific to that sourcevirtualization environment, such as to enable interactions with thesource environment specific to that source environment (e.g., to useAPIs of the source environment that are specific to that sourceenvironment). In other embodiments (e.g., embodiments in which thesource virtualization environment does not provide appropriate APIs),the routine may instead access data corresponding to one or more virtualmachine images in other manners, such as to download hard disk filesfrom the source virtualization environment. In addition, in embodimentsin which a source virtual machine image copy is supplied to the routineby the user, the interactions with the source environment in block 445may not be performed, or instead the interactions may be performed onlyto retrieve additional data (if any) corresponding to the source virtualmachine image.

After block 445, the routine continues to block 450 to determine if theuser has additional configuration information to specify with respect tomodifying the source virtual machine image to execute in a particulardestination virtualization environment, such as a selection of thedestination virtualization environment from multiple availabledestination environment options, selections of capabilities availablefrom a particular destination virtualization environment to be used bythe virtual machine image when executing, etc. If so, the routinecontinues to block 455 to receive one or more additional user selectionsor entries that specify configuration information for aspects of use ofthe source virtual machine image in a destination environment. In somesituations, additional user configuration information may not bespecified in block 455, such as if the user determines to use defaultconfiguration capabilities of the image conversion tool, if the userpreviously specified configuration information to be used, if the userwill later specify some configuration information that is notimmediately needed with respect to the modification activities of block470 or the later execution of the virtual machine image in thedestination environment, etc.

After block 445, or if it was instead determined in block 450 that noadditional user configuration information was received, the routinecontinues to block 470. In block 470, the routine performs one or moremodifications to the extracted data or the source virtual machine toenable the modified data to be used to execute the virtual machine aspart of a particular destination virtualization environment, with themodifications being performed using any user-specified configurationinformation, as described in greater detail elsewhere.

After block 470, the routine continues to block 475 to provide themodified data copy for use in the destination virtualizationenvironment, including to use any user-specified configurationinformation related to activities to be performed as part of providingthe modified data copy. In some embodiments, the routine in block 475will transmit or otherwise send the modified data copy to thedestination virtualization environment, such as if the image conversiontool is executing on one or more computing systems that are remote from(e.g., separated over one or more computer networks) the destinationvirtualization environment. In addition, while blocks 470 and 475 areillustrated as being performed with respect to only a single destinationvirtualization environment in the illustrated embodiment of the routine,in other embodiments the extracted source virtual machine data may bemodified for and used with multiple distinct destination virtualizationenvironments, whether immediately or at later times. In otherembodiments, the providing of the modified data may include providing acopy of the modified data to the user (e.g., by storing it in auser-specified location), such as to enable the user to later supply themodified data to the destination virtualization environment.

If it is instead determined in block 440 that the received input is nota selection or other indication of a particular source virtual machineimage, the routine continues instead to block 490 to perform one or moreother indicated operations as appropriate. Other types of indicatedoperations may include, for example, one or more of the following:receiving a request from a user for status information and respondingaccordingly, such as to enable a user to monitor current status ofperforming a virtual machine conversion and/or to retrieve informationabout historical conversions that were previously performed; receivingone or more types of data from a particular virtualization environment,and storing the data or updating the GUI accordingly (e.g., if aresponse is received from a virtualization environment to anasynchronous request previously sent by the image conversion tool); etc.

After blocks 475 or 490, the routine continues to block 495 to determinewhether to continue, such as until an explicit indication to terminateis received. If it is determined to continue, the routine returns toblock 415 to wait for other input, and otherwise continues to block 499and ends.

FIG. 5 is a flow diagram of an example embodiment of a routine 500 thatmay be performed by a particular source virtualization environment tosupport or otherwise correspond to interactions performed by the imageconversion tool. The routine may be provided by, for example, executionof the manager module 135 of virtualization environment A 120 a of FIG.1, one or more modules (not illustrated) of virtualization environment N120 n of FIG. 1, manager module 232 of FIG. 2, and/or a manager module358 of FIG. 3, such as to provide one or more APIs and respond tocorresponding requests received via those APIs. In at least someembodiments, each source virtualization environment may simultaneouslyperform one or more copies of the routine 500 or a similar routine,and/or different source virtualization environments may simultaneouslyexecute distinct copies of the routine 500 or a similar routine tosupport their own operations (optionally in a manner specific to thatsource virtualization environment). As noted with respect to routine 400of FIGS. 4A and 4B, the illustrated embodiment of the routine 500 isperformed with respect to virtual machine images, but in otherembodiments other types of software images may be supported.

The routine 500 begins at block 505, where a request or data is receivedusing one or more provided APIs. The routine continues to block 510 todetermine if a request is received from an embodiment of the imageconversion tool for information about one or more virtual machine imagesthat are available in the source virtualization environment. If so, theroutine continues to block 515 to retrieve and provide correspondinginformation for the request. If it is instead determined in block 510that a request is not received for information about virtual machineimages, the routine continues to block 530 to determine whether arequest is received from an embodiment of the image conversion tool toprovide data for an indicated virtual machine image. If so, the routinecontinues to block 535 to retrieve one or more hard disks for theindicated virtual machine image and to output the hard disk data in amanner specific to the source environment APIs, or to otherwise retrieveand supply data corresponding to the indicated virtual machine image. Ifit is instead determined in block 530 that a request is not received fordata corresponding to a particular indicated virtual machine image, theroutine continues instead to block 590 to perform one or more otherindicated operations as appropriate, such as to receive and respond toother types of requests from the image conversion tool, to receive andrespond to other types of requests from programs of users of the sourcevirtualization environment, to receive and respond to a user request viathe image conversion tool for information about an account of the userwith the destination virtualization environment; etc.

After blocks 515, 535, or 590, the routine continues to block 595 todetermine whether to continue, such as until an explicit indication toterminate is received. If it is determined to continue, the routinereturns to block 505, and otherwise continues to block 599 and ends.

FIG. 6 is a flow diagram of an example embodiment of a routine 600 thatmay be performed by a particular destination virtualization environmentto support or otherwise correspond to interactions performed by theimage conversion tool. The routine may be provided by, for example,execution of the manager module 195 of FIG. 1, one or more modules (notshown) of the destination execution environment 180 of FIG. 2, and/orthe manager module 378 of FIG. 3, such as to provide one or more APIsand respond to corresponding requests received via those APIs. In atleast some embodiments, each destination virtualization environment maysimultaneously perform one or more copies of the routine 600 or asimilar routine, and/or different destination virtualizationenvironments may simultaneously execute distinct copies of the routine600 or a similar routine to support their own operations (optionally ina manner specific to that destination virtualization environment). Asnoted with respect to routine 400 of FIGS. 4A and 4B, the illustratedembodiment of the routine 600 is performed with respect to virtualmachine images, but in other embodiments other types of software imagesmay be supported.

The routine 600 begins at block 605, where a request or data is receivedusing one or more provided APIs. The routine continues to block 610 todetermine if a request is received from an embodiment of the imageconversion tool related to data to be provided to the routine from theimage conversion tool corresponding to a virtual machine image. If so,the routine continues to block 615 to receive data corresponding to oneor more hard disks of a virtual machine image specified in a mannerspecific to the destination virtualization environment, and stores thedata for later use. In some embodiments and situations, the receiveddata may further include additional information, such as a user withwhom the virtual machine image is associated, about parameter values touse during later execution of the virtual machine, as described ingreater detail elsewhere. If it is instead determined in block 610 thatthe received request is not to provide data for a virtual machine image,the routine continues instead to block 630 to determine whether arequest is received from an embodiment of the image conversion tool toexecute an indicated virtual image, such as a virtual image previouslyprovided by the image conversion tool and stored with respect to block615. If so, the routine continues to block 635 to retrieve the data forthe indicated virtual machine image and to initiate execution of theindicated virtual machine image as part of a virtual machine provided bythe destination virtualization environment. The execution of the virtualmachine image may be performed in accordance with any configurationinformation specified along with the request, or previously specifiedwith respect to the indicated virtual machine image or with respect to auser on whose behalf the image is being executed. If it is insteaddetermined in block 630 that the received request is not to execute anindicated virtual machine image, the routine continues instead to block690 to perform one or more other indicated types of operations asappropriate. Such other operations may include, for example, respondingto other types of requests from the image conversion tool and/or fromother executing programs of users, such as to provide status informationfor a user regarding ongoing execution of an indicated virtual machine(e.g., to enable monitoring of the execution), to provide historicalinformation for a user about previous execution of virtual machineimages, to receive and respond to a user request for information aboutan account of the user with the destination virtualization environment;etc.

After blocks 615, 635, or 690, the routine continues to block 695 todetermine whether to continue, such as until an explicit indication toterminate is received. If it is determined to continue, the routinereturns to block 605, and otherwise continues to block 699 and ends.

It will also be appreciated that in some embodiments the functionalityprovided by the routines discussed above may be provided in alternativeways, such as being split among more routines or consolidated into fewerroutines. Similarly, in some embodiments illustrated routines mayprovide more or less functionality than is described, such as when otherillustrated routines instead lack or include such functionalityrespectively, or when the amount of functionality that is provided isaltered. In addition, while various operations may be illustrated asbeing performed in a particular manner (e.g., in serial or in parallel)and/or in a particular order, it will be appreciated that in otherembodiments the operations may be performed in other orders and in othermanners. It will also be appreciated that the data structures discussedabove may be structured in different manners, including with respect todatabase data structures and Web page data structures, such as by havinga single data structure split into multiple data structures or by havingmultiple data structures consolidated into a single data structure.Similarly, in some embodiments, illustrated data structures may storemore or less information than is described, such as when otherillustrated data structures instead lack or include such informationrespectively, or when the amount or types of information that is storedis altered.

From the foregoing it will be appreciated that, although specificembodiments have been described herein for purposes of illustration,various modifications may be made without deviating from the spirit andscope of the disclosure. In addition, while certain aspects arepresented below in certain claim forms, the inventors contemplate thevarious aspects in any available claim form. For example, while onlysome aspects of the disclosure may currently be recited as beingembodied in a computer-readable medium, other aspects may likewise be soembodied.

What is claimed is:
 1. A system comprising: one or more processors ofone or more computing systems; and one or more memories with storedinstructions of a conversion tool that, when executed by at least one ofthe one or more processors, configure the system to: receive a selectionby a user of a source execution environment that is one of multiplesource execution environments supported by the conversion tool;determine an interaction manner for the selected source executionenvironment that is one of multiple distinct interaction mannerssupported by the conversion tool for use in interacting with themultiple source execution environments, wherein the multiple distinctinteraction manners supported by the conversion tool include interactingvia multiple application programming interfaces (APIs) provided by themultiple source execution environments, and wherein the determining ofthe interaction manner for the selected source execution environmentincludes dynamically selecting a first API to use, wherein the first APIis one of the multiple APIs that is provided by the selected sourceexecution environment and that is different from other APIs of themultiple APIs not used by the selected source execution environment;interact with the selected source execution environment in thedetermined interaction manner to obtain data for a virtual machineprogram that is executable in the selected source execution environment,including performing programmatic interactions over one or more computernetworks to use the first API; modify the obtained data to configure thevirtual machine program to be executable in a destination executionenvironment that is distinct from the selected source executionenvironment; and provide the modified obtained data for use in executingthe virtual machine program in the destination execution environment. 2.The system of claim 1 wherein the performing of the programmaticinteractions over the one or more computer networks using the first APIincludes obtaining a copy of the executable virtual machine programwhile that virtual machine program is being executed by the selectedsource execution environment.
 3. The system of claim 1 wherein theperforming of the programmatic interactions over the one or morecomputer networks using the first API includes accessing and retrievingone or more data files that are stored by the selected source executionenvironment in a format specific to the selected source executionenvironment.
 4. The system of claim 1 wherein the stored instructionsfurther configure the one or more computing systems to provide agraphical user interface of the conversion tool to the user thatincludes information about the multiple source execution environmentssupported by the conversion tool, and wherein the receiving of theselection of the source execution environment by the user is performedvia the provided graphical user interface.
 5. The system of claim 1wherein the source execution environment and the destination executionenvironment are different types of virtualization environments providedby different companies, and wherein at least one of the one or morecomputing systems is further configured to provide the destinationexecution environment and to execute the virtual machine program as partof the destination execution environment based at least in part on theprovided modified data.
 6. The system of claim 1 wherein the sourceexecution environment and the destination execution environment aredifferent types of virtualization environments provided by differentcompanies, and wherein at least one of the one or more computing systemsis further configured to provide the source execution environment andto, before the interacting with the selected source executionenvironment, execute the virtual machine program as part of the sourceexecution environment.
 7. The system of claim 1 wherein the virtualmachine program is a bootable virtual machine image that includesoperating system software and at least one application program.
 8. Thesystem of claim 1 wherein the source execution environment and thedestination execution environment are separated by the one or morecomputer networks, and wherein the one or more computing systems includea first computing system local to the source execution environment thatis configured to execute a first module of the conversion tool andinclude a second computing system local to the destination executionenvironment that is configured to execute a second module of theconversion tool.
 9. A computer-implemented method comprising: receiving,by an image conversion tool executing on one or more configuredcomputing systems, an indication of a source computer virtualizationenvironment that is one of multiple computer virtualization environmentssupported by the image conversion tool; determining, by the executingimage conversion tool, an interaction manner for the source computervirtualization environment, including dynamically selecting a firstapplication programming interface (API) to use that is provided by thesource computer virtualization environment, wherein the determinedinteraction manner is one of a plurality of distinct interaction mannersthat are supported by the image conversion tool and that include using aplurality of other APIs provided by other computer virtualizationenvironments of the multiple computer virtualization environments forinteracting with the other computer virtualization environments;interacting, by the executing image conversion tool, with a computingsystem of the source computer virtualization environment in thedetermined interaction manner to obtain a copy of a virtual machineimage executable by the source computer virtualization environment,including performing interactions over one or more computer networkswith the first API used by the source computer virtualizationenvironment; modifying, by the executing image conversion tool, data inthe obtained copy of the virtual machine image to enable the obtainedcopy of the virtual machine image with the modified data to be used witha destination computer virtualization environment that is distinct fromthe multiple computer virtualization environments; and supplying, by theexecuting image conversion tool, the obtained copy of the virtualmachine image with the modified data to at least one computing systemaffiliated with the destination computer virtualization environment, toenable execution of the virtual machine image in the destinationcomputer virtualization environment based at least in part on themodified data.
 10. The computer-implemented method of claim 9 furthercomprising: interacting, by the executing image conversion tool, with asecond computer virtualization environment of the multiple computervirtualization environments to obtain second data for a second virtualmachine image executable by the second computer virtualizationenvironment, the interacting being performed in a second interactionmanner of the plurality that is specific to the second computervirtualization environment and that is distinct from the determinedinteraction manner; modifying, by the executing image conversion tool,the second data to enable the second virtual machine image to be usedwith the destination computer virtualization environment; and supplying,by the executing image conversion tool, the modified second data to theat least one computing system, to enable execution of the second virtualmachine image in the destination computer virtualization environmentbased on the modified second data for the second virtual machine image.11. The computer-implemented method of claim 9 further comprising:further modifying, by the executing image conversion tool, data in theobtained copy of the virtual machine image to enable the obtained copyof the virtual machine image with the further modified data to be usedwith a second destination computer virtualization environment that isdistinct from the destination computer virtualization environment; andsupplying, by the executing image conversion tool, the obtained copy ofthe virtual machine image with the further modified data to a computingsystem affiliated with the second destination computer virtualizationenvironment, to enable execution of the virtual machine image in thesecond destination computer virtualization environment based at least inpart on the further modified data.
 12. The computer-implemented methodof claim 9 wherein the plurality of distinct interaction mannerssupported by the image conversion tool include accessing and retrievingdata files that are stored by at least one of the multiple computervirtualization environments in a format specific to the at least onecomputer virtualization environment.
 13. The computer-implemented methodof claim 9 wherein the performing of the interactions over the one ormore computer networks with the first API includes obtaining a copy ofthe executable virtual machine image while that virtual machine image isbeing executed by the source computer virtualization environment. 14.The computer-implemented method of claim 9 wherein the performing of theinteractions over the one or more computer networks with the first APIincludes accessing and retrieving one or more stored data files in aformat specific to the source computer virtualization environment. 15.The computer-implemented method of claim 14 wherein the one or morestored data files represent at least one hard disk of the virtualmachine image, and wherein the modifying of the data in the obtainedcopy of the virtual machine image includes changing the format of theretrieved one or more data files to be in a second format that isspecific to the destination computer virtualization environment and isdistinct from the format specific to the source computer virtualizationenvironment.
 16. The computer-implemented method of claim 9 wherein themodifying of the data in the obtained copy of the virtual machine imageincludes adding software to the obtained copy of the virtual machineimage, the added software including at least one of a group includingone or more software libraries, one or more software drivers, or one ormore software application programs.
 17. The computer-implemented methodof claim 9 further comprising: presenting, by the executing imageconversion tool, a graphical user interface to a user of the imageconversion tool, and wherein the received indication of the sourcecomputer virtualization environment is a selection of the sourcecomputer virtualization environment performed by the user via thepresented graphical user interface; and receiving, by the executingimage conversion tool via the presented graphical user interface, aselection of the virtual machine image by the user from multiple virtualmachine images of the source computer virtualization environment, andwherein the interacting with the computing system of the source computervirtualization environment to obtain the copy of the virtual machineimage is performed in response to the selection of the virtual machineimage by the user.
 18. The computer-implemented method of claim 17wherein the at least one computing system is configured to provide atleast some of the destination computer virtualization environment, andwherein the method further comprises: receiving, by the executing imageconversion tool via the presented graphical user interface,configuration information from the user related to execution of thevirtual machine image in the destination computer virtualizationenvironment; and supplying, by the executing image conversion tool, theconfiguration information to the at least one computing system toinitiate execution of the virtual machine image in the destinationcomputer virtualization environment in a manner based at least in parton the configuration information.
 19. The computer-implemented method ofclaim 9 wherein the multiple computer virtualization environments are ofa plurality of distinct types and are provided by a plurality ofcompanies, the plurality of distinct types including multiple of VMWareServer, VMWare Workstation, XenServer, Hyper-V Server, VirtualBox,Kernel-based Virtual Machine, and OpenVZ.
 20. The computer-implementedmethod of claim 9 wherein the virtual machine image is a bootable imagethat is executed by loading the virtual machine image in a providedvirtual machine, the virtual machine image including at least operatingsystem software and software for at least one application program. 21.The computer-implemented method of claim 9 wherein the source computervirtualization environment and the destination computer virtualizationenvironment are separated by one or more computer networks, and whereinthe executing image conversion tool includes multiple modules, at leastone of the modules executing on a first computing system local to thesource computer virtualization environment and at least one other of themodules executing on a second computing system local to the destinationcomputer virtualization environment.
 22. A non-transitorycomputer-readable medium having stored contents that configure one ormore computing systems to execute an image conversion tool and to:receive, by the image conversion tool, a selection by a user of a sourcesoftware image execution environment that is one of multiple sourceexecution environments supported by the image conversion tool;determine, by the image conversion tool, an interaction manner for thesource software image execution environment, including dynamicallyselecting a first application programming interface (API) to use that isprovided by the source software image execution environment, wherein thedetermined interaction manner is one of a plurality of interactionmanners that are supported by the image conversion tool and that includeusing multiple other APIs provided by other of the multiple supportedsource execution environments for interacting with the other supportedsource execution environments; interact, by the image conversion tool,with the source software image execution environment in the determinedinteraction manner to obtain data associated with an executable softwareimage that is in a specified data format specific to the source softwareimage execution environment, including performing interactions over oneor more computer networks to use the first API for the source softwareimage execution environment; modify, by the image conversion tool, theobtained data to be in a second data format specific to a destinationexecution environment that is distinct from the source software imageexecution environment, to enable the software image to be used in thedestination execution environment based on the second data format; andprovide, by the image conversion tool, the modified obtained data foruse in the destination execution environment as part of the softwareimage.
 23. The non-transitory computer-readable medium of claim 22wherein the source software image execution environment and thedestination execution environment are provided by distinct companies,wherein the software image includes at least one application program,and wherein the stored contents include software instructions that, whenexecuted, further configure the one or more computing systems to executethe software image as part of the destination execution environmentbased at least in part on the provided modified obtained data.
 24. Thenon-transitory computer-readable medium of claim 22 wherein the sourcesoftware image execution environment and the destination executionenvironment are distinct types of virtualization environments, whereinthe software image is a bootable virtual machine image that furtherincludes operating system software, and wherein the stored contentsinclude software instructions that, when executed, further configure theone or more computing systems to, before the interacting with the sourcesoftware image execution environment, execute the software image as partof the source software image execution environment.